Deploying with CircleCI

Our automatic deployment system helps to complete the deployment process using special triggers added to the BitBucket commits page of a project that start the automatic deployment process.

For example, to deploy a project to a Staging site, you need to add the stage-{something} tag, and then the deployment will automatically be sent to the remote site.

The entire deployment process will be executed by an automatic CircleCI script, which will prepare all the files for deployment, send them to the right environment, thereby simplifying the deployment process

In the Helium and next projects will be the next flow deploy. By default we will use just Stage and Production. Development will be used just for large projects.

1. We have 3 available environments:
   1. Production,
   2. Stage,
   3. Development.
2. Names of tags which you need to put in order to make deploy:
   1. dev-deploy
   2. stage-deploy
   3. prod-deploy
3. Automatic deploy
   • Dev: Just by adding tag to any branch
   • Stage: Auto deploy after pushing to master, deploy by tag from other branches
   • Prod: There is not auto deploy option. Just by prod-deploy tag and from master ranch only (edi